-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasm] Download Symbols from microsoft symbol server #40690
[wasm] Download Symbols from microsoft symbol server #40690
Conversation
…n there is an exception and exceptions are turned on on debugger. This is a workaround while VS doesn't work on it, which should be the final solution.
I'm not sure what is the best way to receive the symbol server url, I was thinking to receive in the same way that we receive browserUri, and pass to DevToolsProxy in run method. If anyone has any better idea, please let me know. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only nitpicks, nothing to block merging. 👍
What does the server url depend on? Does it change? |
On VsWindows for example, the user can choose a list of symbol server URL. From Microsoft I think that this is the only one. |
re:url, you could send a custom message to the proxy to pass the url, and handle that in How will you get this url from VS though, to pass on to the proxy? |
The custom message that you suggested is the same that I think we should do. |
Co-authored-by: Ankit Jain <radical@gmail.com>
Co-authored-by: Ankit Jain <radical@gmail.com>
…:thaystg/runtime into thays_load_symbols_from_ms_symbol_server
Co-authored-by: Larry Ewing <lewing@microsoft.com>
@lewing , I'm discussing with Diego about how they will pass this info for DebuProxy. |
…request as discussed with Diego: Diego: The response from vs code is that this shouldn't live in js-debug, so I think that passing it around in inspectUri would be the best approach for us
…s_from_ms_symbol_server
Is there anything blocking this now? |
…5.0 without any risk of side effect.
I don't think so, I just removed the default microsoft symbol server URL, then we can try to merge it on rc 2. |
Co-authored-by: Ankit Jain <radical@gmail.com>
Co-authored-by: Ankit Jain <radical@gmail.com>
…il. When it's merged we will not get any side effect with this workaroud.
@lewing I removed the default URL of MS Symbol Server, so now, this will not affect the user unless he changes the LaunchSettings.json to use this InspectUri: |
/backport to release/5.0-rc2 |
Started backporting to release/5.0-rc2: https://github.com/dotnet/runtime/actions/runs/256085151 |
Creating a draft to download symbols from microsoft symbol server when there is an exception and exceptions are turned on on debugger.
This is a workaround while VS doesn't work on it, which should be the final solution.
If you think that is in the right way, there is still a to do list:
The callstack exception without this PR:
The callstack exception with this PR: